Method and system for remote access of personal music

ABSTRACT

In one aspect of the invention, a method is provided for storing audio files. The method includes: (a) receiving electronic files at a central location from a first device, those electronic files representing audio signals; (b) associating the audio files with identification information; (c) storing the audio files at the central location on at least a portion of a storage media, that portion being uniquely associated with the identification information; (d) receiving the identification information from a second device; and (e) transmitting the audio files to the second device upon receipt of the identification information.

The present application claims the benefit of U.S. ProvisionalApplication No. 60/203,684, filed on May 12, 2000, which is herebyincorporated by reference.

BACKGROUND OF THE INVENTION

Many consumers today have amassed substantial music collections in theCD audio format. The physical aspect of such a large collection howevermeans that a consumer wishing to enjoy their collection from any placeother than where the collection is located must make a choice as towhich CD to take with them as they move about.

The primary alternative to date has been for the consumer to recordselect CD's onto cassette tape or mini-disc mediums to take with themwhen they leave the vicinity of their music collection. By default, thismeans the entire collection is not remotely available for the consumer'senjoyment.

As a newer alternative, the advent of the MPEG-based MP3 file format hasenabled consumers to record (rip) their CD's and store them as MP3 fileson their personal computers. This does enable a degree of addedflexibility, however as the number of files is limited by the availablehard disk drive space in the consumer's PC, it is also an inadequatesolution. Since a typical album requires approximately 30-60 mb of harddisk space, the storage requirement of this and similar file formatsonce again forces the consumer to choose which elements of their musiccollection they want to enjoy instead of having access to the entirecollection.

There is thus a need for a system which allows users both mass storageand portability.

SUMMARY OF THE INVENTION

The present invention meets those needs.

In one aspect of the invention, a method is provided for storing audiofiles. The method includes (a) receiving electronic files at a centrallocation from a first device, those electronic files representing audiosignals; (b) associating the audio files with identificationinformation; (c) storing the audio files at the central location on atleast a portion of a storage media, that portion being uniquelyassociated with the identification information; (d) receiving theidentification information from a second device; and (e) transmittingthe audio files to the second device upon receipt of the identificationinformation.

In another aspect of the invention, a system is provided for storing andtransmitting audio information. It includes a processor, memory, datastored in the memory and instructions executable by the processor. Thedata identifies a plurality of users or devices and also includes aplurality of files associated with audio information. Each of the filesis uniquely associated with the identity of a single user or device. Theset of instructions also conditions the transmission of a song from thesystem to a user or device based on the identity of the user or deviceassociated with the audio information.

In yet another aspect, a method of storing and transmitting songsincludes: uniquely associating a portion of the storage space on aserver with a user or device; associating the portion with a firstidentifier; receiving the first identifier; receiving a song filerepresentative of a song; storing the song file in the portion of thestorage space associated with the first identifier; receiving a secondidentifier and a request for the song file; comparing the secondidentifier with the identifier associated with the requested song file;and transmitting the song file in response to the request depending uponthe outcome of the step of comparing.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional diagram of a system in accordance with anembodiment of the invention.

FIG. 2 is a functional diagram of a content provider in accordance withan embodiment of the invention.

FIG. 3 is an example of memory allocation in accordance with anembodiment of the invention.

FIG. 4 is a flow chart of operations in accordance with an embodiment ofthe invention.

FIG. 5 is a functional diagram of another content provider in accordancewith an embodiment of the invention.

FIG. 6 is a functional diagram of device information data stored in acontent server in accordance with an embodiment of the invention.

FIG. 7 is a functional diagram of a user storage area in accordance withan embodiment of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

As shown in FIG. 1, a system 50 in accordance with one embodiment of theinvention comprises a network of devices such as end user personalcomputer 60, web servers 70-71, PDA 73 and car-audio system 72, all ofwhich communicate via Internet 80. Although only a few devices aredepicted in FIG. 1, it should be appreciated that a typical system caninclude a large number of connected devices. Preferably, end usercomputer 60 is a general purpose computer having all the internalcomponents normally found in a personal computer such as, for example,central processing unit (CPU) 61, display 62, CD-ROM 63, hard-drive 64,mouse 65, keyboard 66, speakers 67, microphone 68, modem 69 and all ofthe components used for connecting these elements to one another. Enduser computer 60 communicates with the Internet 80 via modem 69. Enduser computer 60 may comprise any workstation capable of processinginstructions and transmitting data to and from humans and othercomputers, including network computers lacking local storage capability.

Also connected to network 80 is a personal digital assistant (PDA) withwireless capability having all the internal components normally found ina PDA such as, for example, a processor 78, touch-sensitive display 75,buttons 77, modem 76 and all of the components used for connecting theseelements to one another. The buttons 77 and touch-sensitive display 75are typically used for data entry. The PDA also includes a headphonejack for use with headphones 74. The processor executes instructionsstored on a storage medium, such as RAM 79. Although a PDA is shown byway of example in this embodiment of the present invention, it should beunderstood that the PDA may also comprise other mobile devices, such asInternet-capable wireless phones.

Car audio system 72 also communicates with Internet 80 via a wirelesscommunication. The car audio system includes a receiver (not shown) forreceiving electronic information over the Internet and a speaker (notshown) for playing the audio signals contained in the audio information.

Web server 70 contains hardware for sending and receiving informationover the World Wide Web, such as web pages or files. The web server 70may be a typical web server or any computer network server or otherautomated system capable of communicating with other computers over anetwork, including the Internet, wide area networks or local areanetworks. For example, the system described above in connection with enduser computer 60 may also function as a web server.

Moreover, the system is not limited to the World Wide Web or theInternet but, rather, is applicable to any network allowing remotecommunication to a central storage area by multiple devices.

As shown in greater detail in FIG. 2, web server 70 functions as acontent store and contains a processor 102, a set of instructions 104which are executed by processor 102 and data such as user storage area110. The functions, methods and routines of the program are explained inmore detail below. Although the data is shown separately from theinstructions, the data may be modified by the processor during executionof the instructions. Moreover, both the data and the instructions may bestored as a program on the hard disk of the server 70.

User storage area 110 is used to store the user music files 114 uploadedby the users. Preferably, each user has a predefined amount of spaceallocated to its sole use, and no other user is permitted unauthorizedaccess to any information stored in its particular space. Each user hasa User ID 112 which identifies the space allocated to the user. Forillustration purposes, three different user spaces are schematicallyshown in FIG. 2 for users with ID's “User1”, “User2” and “User3”. User1has three music files stored in its space, including files called“File1”, “File2” and “File3” corresponding with songs named “SongA”,“SongB” and “SongC”, respectively. User2 also has a file stored in itsspace designated as “File4”. However, as indicated by the “SongA” labelin parenthesis next to “File4”, that file may be the same song as—andbyte for byte a copy of—“SongA” contained in File1, of User1. File1 andFile4 may also be quite different even if the song is the same, such asif the same song was encoded at two different frequencies. FIG. 2 alsoshows User3 as having three music files, “File5”, “File6” and “File7”corresponding with “SongD”, “SongE” and “SongA” (again), respectively.

The manner in which songs are stored and occupy user storage area 100 isalso shown schematically and to scale in FIG. 3. In the diagram, thewidth of a cell relates to the size of the associated file. The width ofeach cell in row 150 relates to 1 MB of data. As can be seen, assumingthat each user has stored the exact same copy of the SongA music file,the music file will take up the same amount of space in each individualuser's space 152-54. If desirable, the system may limit each user to aparticular amount of storage space, such as 100 megabytes of music.

In operation in accordance with one embodiment, music is stored on theserver in accordance with the steps shown in the flowchart of FIG. 4.First, the user encodes audio compact discs from red book format or ananalog source into electronic digital files (step 202). The files arepreferably compatible with MPEG-3 format or Sony's ATRAC3 format and areencoded with a general purpose computer, such as computer 60, or adedicated device. The user then causes end user computer 60 to accessthe content server 70 via the Internet 80 (such as by logging onto a webpage) (step 204), supplies its User ID 112 (step 206) and then uploadsthe files to the content server 70 (step 208). Using the foregoingexample of FIG. 2, User1 would take a compact disc it owned, encode“SongA” as a digital file on end user computer 60 and upload the digitalfile to the content server 70 via Internet 80. In so doing, the useridentifies the song with a string, such as “File1”.

Upon receipt of the User ID 112 and the song file, processor 101 ofserver 70 in accordance with instructions 104 first checks the size ofthe file to make sure that the user has not exceeded its space limit(step 209). If the user has, then an error notification will be sent tothe user explaining the problem (step 211). Otherwise, processor 101will store the uploaded file into the space allocated for the particularuser (step 210), and associate the file with the identifying stringprovided by the user.

The operation of downloading the music is also shown in FIG. 4. In thisembodiment, the user accesses the content server 70 (such as by loggingonto a web page) via PDA 73 which, for the purposes of this example,shall be considered to be at a geographic location remote from end usercomputer 60 (step 220). In other words, although the user uploaded thesongs with one device, the user may download the songs at a differentlocation with a different device. The user accesses the web sitemaintained by content server 70 by using wireless modem 76 in a mannerwell known to those of ordinary skill in the art. The user next suppliesits User ID to content server 70 by entering the information on a webpage displayed on screen 75 (step 222). For example, the user mayidentify itself as “User1” (it is recommended, but not required, thatuser names be more arbitrary than a designation of “User1” for securityreasons). Optionally, the song may be identified at the same time aswell. Processor 101 of server 70 searches user storage area 110 to seewhether there is any user associated with that particular ID (steps 224and 226). If the user ID is not found, an error notification is sent tothe user to that effect (step 211).

If the user ID is found, the server 70 checks whether it has alreadybeen provided with an identification of the song to be downloaded (step228). If not, then server 70 may, optionally, send a list of theidentifying strings to the user (step 230). For example, server 70 wouldsend the strings “File1”, “File2” and “File3” if the songs matched theillustrative examples in FIG. 2. These strings could be displayed onscreen 75. Content server 70 next prompts the user to enter theidentifier for the song, which may be entered via touch-screen 75 (step232).

The identifier for the song is checked against the list of songsassociated with that user (step 234). Using the example values of FIG.2, the string “File1” would be valid identifier because there is a songfile having that identifier contained in User1's space. The string“File4”, on the other hand, would not be a valid identifier even thoughit points to a byte-for-byte identical file with the same name inUser2's space. Accordingly, the identifier must identify a songcontained in the respective user's space. If the song with thatidentifier is not contained in the space allocated to that user in userstorage user 110, the user is notified of the error (step 211).

If the song is validly identified, the song is then sent from the server70 to the PDA 73 (step 236). Once downloaded, the song may then beplayed by the user (step 240).

Accordingly, each user is assigned a unique identification code suchthat the user (or the entity to whom the user gives the code) is theonly entity that can upload and download music to and from the storagespace allocated to the user. This identification code is sent with, orbefore, the steps of uploading and downloading and is used to verifythat the requester is the user associated with the particular storagespace. It is not necessary for the server to set aside, in advance,actual portions of the storage space to particular users. Rather, thefiles may be first stored (and thus occupy a portion of the hard driveof the server) and access permissions set for the file set in accordancewith the identify of the user.

After the music is uploaded by the user to the central location, it maybe played anywhere by any device capable of connecting with the server.For example, if the online service provider hosts a website, the userprovides its unique identification code and the online service providerauthenticates the user. The user may then download, via the internet, acopy of one or more of the music files that had been uploaded by theuser.

Rather than downloading the music, the music may also be streamed to theuser. Security choices may dictate whether the music file is served viaa streaming process or a download, as streaming places more of arequirement on the connection but downloads place more of a resourcerequirement on the device. For the purposes of this disclosure, the word“download” should be understood to include real-time streamingregardless of whether the transmitted information may be permanently andlocally stored.

One of the advantages of the system is that there is a copy of a songfor every user, rather than giving one copy of a song to multiple users.Moreover, the user is responsible for maintaining the songs stored intheir space. Thus, the invention facilitates respect for copyrightowner's rights to prevent multiple unauthorized parties from downloadingthe same song.

Preferably, the system provides music to dedicated devices byautomatically authenticating the devices upon connection. In such anembodiment, each device that accesses songs stored in content server 70has an identifier which is unique to the system. For example, such anidentifier may be a GUID. The unique identifier may also be a numberstored in the RAM or other readable/writable storage media of thedevice, such as RAM 79 of PDA 73. This information may be stored in theuser storage area of content server 70 as shown in FIG. 7. For each UserID 612 in the user storage area, there are not only songs 614 but also alist of device identifiers 616. For example, the identifier “Device1”may be the value of the device identifier stored in a network-enabledWalkman® player operated by User1, “Device2” may be the value of thedevice identifier stored in the car audio system 72 operated by the sameUser1, “Device3” may be the value of the device identifier stored in enduser computer 60 operated by User1, and “Device4” may be the value ofthe device identifier stored in a Clie™ PDA operated by User1.

In one possible operation of such a system, the device connects with thecontent server via the Internet (FIG. 4; step 250). The deviceautomatically transmits its unique identifier (step 252). In response,the processor of the content server searches the device identifiers 616to determine the associated user ID (step 254). If a user ID is found,then the process proceeds as described above.

Preferably, the system also has the ability to limit the number of songsthat a consumer can download or stream to, either simultaneously or intotal. In such an embodiment and as shown in FIG. 6, each content server70 counts how many times a file has been downloaded. The processor alsodecrements that value each time it is downloaded. For example, if adevice designated as “Device1” was given a trial period to listen toSong A, then content server 70 may store the value “5” in the CopiesLeft field 513 of the user storage area, thus indicating that the devicemay download the song 5 times. Each time the song is downloaded, thevalue decrements. For example, FIG. 6 shows that “Device2” may onlydownload the song 3 more times. However, if SongA were purchased, thenthe device would be able to download the song any number of times (suchas is shown for “Device3”).

Limiting the authorization to a particular device or user has its ownunique advantages. If the authorization is limited to a particular userID, which is not wedded to a particular device, then a user may grantaccess to friends and associates by passing along his or her ID. On theother hand, if a more secure environment is required, then the device IDmay be hardwired into the unit, such as GUID. Preferably, the contentserver 70 will allow both possibilities. Thus, certain songs, such assound clips, may be freely transferable provided you have a particularuser ID. Different songs, on the other hand, would be limited to aspecific number of plays on a particular device. Access can thus belimited to particular devices or could provide the user with full“owner” access.

In another embodiment, the user does not encode and upload the songthemselves. Rather, the user buys a copy of the music from the contentserver 70 and the file is stored in the user's space. Specifically, asshown in FIG. 5, content server 70 includes a database of musicselection. This database, song bank 400, stores a plurality of songs asmusic files. The songs are designated by name 401, a description 402 andthe price of the song 403.

In the operation of this embodiment, the user will access the contentserver and obtain a list of music selections which are available for use(step 302 of FIG. 4). For example, a list of the songs, theirdescriptions and prices may be sent as a web page to end user computer60. The user selects the songs that they would like and then transmitsthat information, along with their User ID, to the content server 70(step 304). For example, “User 2” may indicate that they wish to listento “Song X”. Upon receiving the name of the song from the user,processor 101 then extracts the file associated with the song from thesong bank 400 (step 306). The process then proceeds as if the song hadbeen uploaded by the user, i.e. the processor 101 checks the size of theselected song against the space remaining available to the user (step209). If there is enough room, the song is stored in the area allocatedto the particular user (step 210) as schematically indicated by thedashed arrow in FIG. 5. Accordingly, in this embodiment, even when acopy of the song is available on the server, yet another copy of thesong will be stored in the user's space in user storage area 110. Thedatabase may also be contained at a separate site or server, such asserver 71 of FIG. 1.

The embodiment shown in FIG. 2 permits other interesting options andvariations. For example, the system may deploy a security system such asthose currently being contemplated by the music industry for online usesuch as SDMI. The user may be able to “check” particular songs in andout of song bank 400. If one user has loaded the song onto its system,then no other user would be permitted to listen to the song, thuspreventing multiple parties from simultaneously playing or using thesame song. Such an embodiment may be implemented as shown by step 702 ofFIG. 4, whereby a song may only be uploaded into a user's space if it isnot checked out to someone else. The song could be checked back in inany number of different ways, such as the user simply informing thecontent server that it has finished listening to the song or countingthe number of streaming downloads (as discussed in connection with FIG.6) and checking it back in when the Copies Left field 513 reaches zero.In other words, the system is geared to prevent unauthorized multiplecopies of a single authorized copy. This helps prevent piracy and theinappropriate use of the music collection stored on the network.

Another one of the myriad advantages of the present invention is thatusers are able to access music from any location without having to carrymedia containing the music. A user may place a copy of its music at acentral location and play that music from any remote location. Anotheradvantage is that the authentication mechanism protects third party'srights in the user's music but still preserves the foregoing advantageof portability. Moreover, by providing a unique storage area at acentral location, the user can access the music regardless of whether ornot the device used to encode or upload the music is powered on or not.In other words, the consumer may upload their entire music collection toa system server operated as an independent service and will then be ableto access the entire collection from anywhere in the world, from anydevice connected to the Internet and equipped with audio-enabled andbrowser technology. The rapidly advancing availability of wired andwireless Internet connectivity means a music-loving consumer can readilyaccess their entire collection from any place they can connect.

Another advantage of the invention is that it can accommodate securityrequirements. For example, the central server may also check music forsecurity limitations before permitting the music file to be stored.

Additionally, because the user is able to upload the music they want,the user can create unique compilations in accordance with the user'spersonal preferences. The user can thus create compilations directed toparticular genres of music (such as dance or exercise). Optionally, theuser may also change the order that the songs are downloaded orstreamed.

In another implementation, the first time the consumer plays a new CDthey are adding to their collection, their Internet connected CD playeror changer would upload the file to the network server for storage. Thisupload process could be implemented in variety of ways including thedisc-by-disc upload from the CD-ROM drive of a PC connected to theInternet or from a new service-based business designed to transfer theconsumer's collection in total. The file format used could be any of theknown or to be developed formats given file size, sound quality, andsecurity trade-offs.

In addition, because the network is functioning as the storage facilityfor the consumer's audio collection, the network could employ preferencemining techniques as to the collection's content and frequency of use aswell as device context. Such data mining would enable the network toactually recommend selections from the collection to match particularactivities or to suggest new music which might be enjoyed by the sameconsumer.

Unless stated to the contrary, use of the words such as “including,”“containing,” “comprising” and the like, means “including withoutlimitation” and shall not be construed to limit any general statementthat it follows to the specific or similar items or matters immediatelyfollowing it.

Most of the foregoing alternative embodiments are not mutuallyexclusive, but may be implemented in various combinations to achieveunique advantages. As these and other variations and combinations of thefeatures discussed above can be utilized without departing from theinvention as defined by the claims, the foregoing description of theembodiments should be taken by way of illustration rather than by way oflimitation of the invention as defined by the claims.

1. A method of storing audio files comprises: (a) receiving at a centrallocation electronic files representing audio signals from a firstdevice, (b) associating the audio files with authenticationidentification information of a user, (c) storing said audio files atsaid central location on at least a portion of a storage media, saidportion uniquely associated with said authentication identificationinformation, (d) receiving at said central location said authenticationidentification information from a second device, (e) transmitting saidaudio files to said second device upon receipt of said authenticationidentification information.
 2. The method of claim 1 wherein said serveris a web server and said files and information are received andtransmitted via the Internet.
 3. The method of claim 1 wherein at leastone of said devices is a general purpose computer.
 4. The method ofclaim 3 wherein at least one of said devices is a personal computer. 5.The method of claim 1 wherein said second device is installed in anautomobile.
 6. The method of claim 1 wherein at least one of saiddevices is a personal digital assistant.
 7. The method of claim 6wherein said personal digital assistant receives said audio files viawireless communication.
 8. The method of claim 1 further comprisingencoding said electronic files from a source of audio information. 9.The method of claim 8 wherein said source is a compact disk.
 10. Themethod claim 1 wherein said electronic files are compatible with theMPEG format when received at said central location.
 11. The method claim1 wherein said electronic files are compatible with the ATRAC3 formatwhen received at said central location.
 12. The method of claim 1further comprising receiving said authentication identificationinformation from said first device.
 13. The method of claim 1 whereinsaid step of receiving at said central location said authenticationidentification information comprises said second device automaticallysending said authentication identification information to said centrallocation.
 14. The method of claim 12 or 13 wherein said authenticationidentification information is associated with said device.
 15. Themethod of claim 14 wherein said first device and said second device arethe same device.
 16. The method of claim 15 wherein said step ofassociating said audio files with identification information comprises auser sending information which identifies the user.
 17. The method ofclaim 1 wherein said identification information is sent from said firstdevice when said first device is connected to said central location viaa network.
 18. The method of claim 17 wherein said network is theInternet.
 19. The method of claim 18 wherein said authenticationidentification information is sent automatically by said first andsecond devices to said central location.
 20. The method of claim 1further comprising the step of receiving at said central location arequest for at least one of said files and wherein said step oftransmitting comprises transmitting said at least one of said files. 21.The method of claim 20 further comprising the step of comparing theidentification information associated with said requested file with theidentification information received during said step of receiving saididentification information from said second device, and said step oftransmitting is conditional upon the results of said comparison.
 22. Themethod of claim 21 further comprising the step of transmitting to saidsecond device a list of the files associated with the identificationinformation received from said second device.
 23. The method of claim 22further comprising comparing the size of the electronic file with theamount of said portion uniquely associated with said identificationinformation, and wherein performance of said step of storing isconditional upon the result of such comparison.
 24. The method of claim23 further comprising transmitting a notification to the user if thesize of the electronic file plus the size of other files stored in saidportion is greater than the amount of said portion.
 25. The method ofclaim 1 wherein said second device is at a geographic location remotefrom said first device.
 26. The method of claim 1 wherein said step oftransmitting comprises downloading said file.
 27. The method of claim 26wherein said step of transmitting comprises streaming said file to saidsecond device.
 28. The method of claim 26 wherein said step oftransmitting comprises permitting said second device to permanentlystore said file.
 29. The method of claim 1 further comprising: (a)receiving at said central location electronic files representing audiosignals from a third device, said third device having differentidentification information, (b) storing the audio files from said thirddevice on a portion of said storage media that is different from theportion uniquely associated with said identification informationassociated with said audio files from said first device.
 30. The methodof claim 1 wherein the authentication identification informationcomprises a GUID.
 31. The method of claim 1 wherein the central locationis configured to permit concurrent submission of the authenticationidentification information of the user and audio file identificationinformation by the second device.
 32. A system for storing andtransmitting audio information comprising: a processor; memory; datastored in said memory, said data identifying a plurality of users ordevices, said data further comprising a plurality of files associatedwith audio information, each said file being uniquely associated withthe identity of a single user or device; a set of instructionsexecutable by said processor, said instructions conditioning thetransmission of a song from the system to a user or device based on theidentity of the user or device associated with said audio information.33. The system of claim 32 wherein the total size of files stored insaid data for a particular user or device is limited.
 34. The system ofclaim 33 wherein a file associated with a first user is identical to afile associated with a second user and said data comprises two copies ofsaid file.
 35. The system of claim 32 wherein said system comprises aserver.
 36. The system of claim 35 further comprising an audio playerconnected via a network to said server, said audio player beingidentified by at least some of the data identifying a plurality of usersor devices.
 37. The system of claim 36 wherein said audio playercomprises memory containing information identifying said player.
 38. Thesystem of claim 37 wherein said audio player further comprises a speakerand a processor for playing said file.
 39. The system of claim 37wherein said audio player sends the identification informationautomatically to said server.
 40. The system of claim 37 wherein saidremote device is a PDA.
 41. The system of claim 37 wherein theidentification information comprises a GUID.
 42. The system of claim 32wherein said identification information comprises a portable audioplayer.
 43. The system of claim 32 wherein the set of instructionsexecutable by said processor permit concurrent submission of theidentity of the user and a song identification as a condition of thetransmission of the song.
 44. A method of storing and transmitting songscomprising: uniquely associating a portion of the storage space on aserver with a user or device, the storage space to store song files eachhaving a filename; associating said portion with a first userauthentication identifier; receiving said first user authenticationidentifier; receiving a song file representative of a song; and storingsaid song file with a filename in the portion of said storage spaceassociated with said first user authentication identifier; receiving asecond authentication identifier and a request for said song file;comparing said second authentication identifier with the first userauthentication identifier associated with said requested song file;transmitting said song file in response to said request depending uponthe outcome of said step of comparing.
 45. The method of claim 44wherein if a first file is received along with a first identifier and asecond file is received along with a second identifier and said firstfile and second file are identical copies of one another, then saidfirst file is stored on a portion of said storage space different fromthe portion where said second file is stored.
 46. The method of claim 45further comprising the step of tracking the number of times a song filehas been transmitted.
 47. The method of claim 44 wherein said step ofstoring said song file in the portion of said storage space associatedwith said first identifier occurs prior to said step of associating saidportion with a first identifier.
 48. The method of claim 44 wherein saidstep of receiving said song file comprises receiving said song file fromsaid user.
 49. The method of claim 44 wherein said step of receivingsaid song file comprises receiving said song file from a bank of songfiles.
 50. The method of claim 49 further comprising the step of saidsong bank preventing access to said song file stored at said song bankfor an amount of time.
 51. The method of claim 50 wherein said amount oftime is determined by the number of times a user is permitted todownload the song.
 52. The method of claim 44 further comprisingreceiving concurrent information in a request, the concurrentinformation comprising a request for a particular song filerepresentative of a song and said first user authentication identifier;and transmitting the song file upon authenticating the request with thefirst user authentication identifier.
 53. A method for storing audiofiles for use by multiple users to prevent access to an authorizeduser's audio files by other authorized users comprising: (a) receivingat a central system a plurality of electronic files representing audiosignals for the purpose of storing the plurality of files at the centralsystem for multiple users, (b) storing a plurality of sets of electronicfiles of the plurality of audio files at the central system, each setbeing uniquely associated with authentication identification informationof a user, (c) receiving at said central location authenticationidentification information of a user from a device, and (d) transmittingaudio files of a set of audio files to said device upon receipt of saidauthentication identification information of the user; wherein differentstored sets of electronic files of the plurality of audio files on thecentral system are exclusively accessible to different authenticationidentification information.
 54. A method for storing audio files for useby multiple users to prevent access to an authorized user's audio filesby other authorized users comprising: (a) receiving at a central systema plurality of electronic files representing audio signals for thepurpose of storing the plurality of files at the central system formultiple users, (b) storing a plurality of sets of electronic files ofthe plurality of audio files at the central system, each set beinguniquely associated with authentication identification information of auser, (c) receiving at said central location authenticationidentification information of a user from a device, and (d) transmittingaudio files of a set of audio files to said device upon receipt of saidauthentication identification information of the user; wherein differentstored sets of electronic files of the plurality of audio files on thecentral system are exclusively accessible to different authenticationidentification information, wherein the central location is configuredto permit concurrent submission of the authentication identificationinformation of the user and audio file identification information fromthe device for transmitting at least one of the audio files to thedevice, without first transmitting a song selection list to the device.